Skip to content

Conversation

@ricardozanini
Copy link
Member

Many thanks for submitting your Pull Request ❤️!

Fix #1035

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@ricardozanini ricardozanini requested a review from a team as a code owner April 3, 2025 23:30
@ricardozanini ricardozanini added area:client This item is related to the client extension backport-main-lts labels Apr 3, 2025
Copy link
Member

@mcruzdev mcruzdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you believe that I started something related for server extension today? I left a comment @ricardozanini!

* Sample</a>
*/
@ConfigItem(name = ConfigItem.PARENT)
public Map<String, String> authConfigParams;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is @WithParentName not necessary here?

Copy link
Member Author

@ricardozanini ricardozanini Apr 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? This implementation was lazy then, leaving it as a can-be-anything string. Now we have settled the properties in the API so that the birds can chirp again.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh you mean in username? No, we don't need it. The IDE with Quarkus plugin installed now recognizes these properties beautifully.

@ricardozanini ricardozanini requested a review from fjtirado April 4, 2025 02:12
@ricardozanini
Copy link
Member Author

@hbelmiro any thoughts?

@ricardozanini ricardozanini merged commit 81ca0f5 into quarkiverse:main Apr 4, 2025
11 checks passed
@ricardozanini ricardozanini deleted the issue-1035 branch April 4, 2025 20:43
github-actions bot pushed a commit that referenced this pull request Apr 4, 2025
hbelmiro pushed a commit that referenced this pull request Apr 5, 2025
Signed-off-by: Ricardo Zanini <[email protected]>
Co-authored-by: Ricardo Zanini <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:client This item is related to the client extension backport-main-lts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Config Key warning but functionality works

3 participants